Skip to content

Add glances config#1

Merged
aptalca merged 2 commits intomasterfrom
glances
Nov 20, 2018
Merged

Add glances config#1
aptalca merged 2 commits intomasterfrom
glances

Conversation

@aptalca
Copy link
Copy Markdown
Member

@aptalca aptalca commented Nov 20, 2018

linuxserver.io

Thanks, team linuxserver.io

@aptalca aptalca merged commit b7271d8 into master Nov 20, 2018
@aptalca aptalca deleted the glances branch November 20, 2018 00:53
aptalca pushed a commit that referenced this pull request May 19, 2019
@YouveGotMeowxy
Copy link
Copy Markdown

YouveGotMeowxy commented Sep 13, 2022

Can anyone help me with this one? I'm using the current glances subdomain conf and still get a 502 Bad Gateway error. My Compose looks like this, but I cant find what could be the issue?

  glances:
    hostname: 'glances'
    image: 'nicolargo/glances:alpine-latest-full'
    pid: 'host'
    environment:
      GLANCES_OPT: '-w'
    volumes:
      - '/opt/docker/configs/glances/glances.conf:/glances/conf/glances.conf:ro'
      - '/var/run/docker.sock:/var/run/docker.sock:ro'
    network_mode: 'host'
    ports:
      - '127.0.0.1:61208:61208'
      - '127.0.0.1:61209:61209'
    deploy:
      mode: 'replicated'
      replicas: 1
      placement:
        constraints:
          - 'node.labels.Main == true'
      restart_policy:
        condition: 'any'

I've made no changes to the glances.conf, I have just mounted it for persistence in case I modify it down the road. I suspect it's something obvious that I'm just missing?

Also just a side question; do I need the "full" version of glances in this case, or will it run fine with the "small" version?

TIA!

@aptalca
Copy link
Copy Markdown
Member Author

aptalca commented Sep 13, 2022

Don't run it in host networking

@YouveGotMeowxy
Copy link
Copy Markdown

Don't run it in host networking

ok, thank you, I will try that. Will that remove the stats that glances is supposed to show for the host machine?

@aptalca
Copy link
Copy Markdown
Member Author

aptalca commented Sep 13, 2022

I don't know as I don't use it. But if you do use host networking, then you need to set upstream_app in the proxy conf to the host's lan ip instead of the container name

Roxedus pushed a commit that referenced this pull request Nov 29, 2022
Create mattermost.subdomain.conf.sample
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants